Techniques for mobile transaction processing

ABSTRACT

Techniques for automated mobile transaction processing are provided. A consumer traverses to a web portal or other type of enterprise terminal device of an enterprise and proceeds to shop. During checkout, the portal contacts a transaction service and is delivered back an identifying barcode or Quick Response (QR) code. The consumer uses a mobile device to scan the code and send it to the transaction service. Previously registered payment details of the consumer are located and payment is received from the consumer. The portal is notified that payment is completed by the transaction service.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a divisional application and claims thebenefit of the filing date of application Ser. No. 13/285,371, filedOct. 31, 2011, entitled, “Techniques for Mobile Transaction Processing”.

BACKGROUND

Consumers are increasingly using kiosks to conduct business withenterprises. The kiosks come in a variety of sizes and are used for avariety of purposes. Some kiosks are drive through, such as fast foodestablishments, pharmacies, banks, and the like. Other kiosks arestationary located in gas stations, airlines, grocery stores, departmentstores, and the like.

In addition, what is considered a kiosk is evolving with today'stechnology. For example, digital signs now provide advertisements andmechanisms for users to interact with the displays to performtransactions. Such mechanisms include blue tooth communication, NearField Communication (NFC), Quick Response (QR) code scanning, WiFicommunication, and the like.

So, increasingly customers are engaging in a variety of technologies toautomatically interact with enterprises to perform transactions. Thetransactions may result in purchases or may result in such things asregistration for loyalty programs, enrolling in promotional events,requesting additional information for a good or service, and others.That is, the transactions via these kiosks are not strictly tied topurchases although some transactions are purchase related.

One problem with the variety of existing mechanisms used to interactwith customers is that often the customers are required to enter avariety of identifying information or other information before atransaction can conclude. For example, nearly all enterprise kiosks orwebsite portal stores require the consumer to enter payment information,such as a bank account number or credit card number. This poses asecurity risk that some consumers do not want to engage in. It alsoslows down the transaction and if the consumer enters one wrong numberfor an account the whole transaction can be denied.

SUMMARY

In various embodiments, techniques for automated transactions with anenterprise are presented. According to an embodiment, a method for anautomated transaction with an enterprise system is provided.

Specifically, a request is received to complete a transaction occurringbetween a consumer and an enterprise terminal device. Next, a uniquetoken is provided back to the enterprise terminal device for uniquelyidentifying the transaction. Subsequently, a signed version of theunique token is received from the mobile device and the signed token isvalidated. Finally, the transaction is completed using payment detailsassociated with the consumer.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a flow diagram for mobile transaction processing, according toan example embodiment.

FIG. 2 is a diagram of a method for mobile transaction processing,according to an example embodiment.

FIG. 3 is a diagram of another method for mobile transaction processing,according to an example embodiment.

FIG. 4 is a diagram of yet another method for mobile transactionprocessing, according to an example embodiment.

DETAILED DESCRIPTION

FIG. 1 is a flow diagram for mobile transaction processing, according toan example embodiment. The components of the diagram are implemented innon-transitory computer-readable storage medium for execution on one ormore processing devices that are configured to execute the components.The components are also enabled to operate and communicate with oneanother over a network. The network can be wired, wireless, or acombination of wired and wireless.

It is noted that the components and the interactions of the componentsshown in the FIG. 1 are presented for illustrative purposes in a samplescenario with a sample enterprise system. So, other arrangements andinteractions of the components are possible without departing from thebeneficial teachings presented herein and below.

Various embodiments herein provide a mechanism to enable a consumer topresent their payment and/or loyalty information online. A web shoppingsite presents a Two-Dimensional (2D) barcode to the consumer, who scansthe barcode in with their mobile device, accomplishing the same endresult as entering their credit card information. This also establishesa link between the consumer mobile device and the transaction—such thatthe mobile device can be used as the User Interface (UI) to allow thecustomer to answer questions, redeem points, pay, or transact othersecure business on their mobile device in a “trusted” environment.

Referring to the FIG. 1, a consumer visits a commercial website with theintention of making a purchase; this can occur via a different devicefrom a mobile device of the consumer or via the same mobile device.

The consumer uses the traditional web shopping model to add items totheir cart and proceeds to checkout.

The business web application calls a mobile transaction web service witha transaction Identifier (ID), unique session ID, or other informationnecessary to conduct the transaction.

The Transaction System returns barcode and string data containing theportal Uniform Resource Locator (URL) and the unique transaction ID,digitally signed with the private key of the business.

The web site displays the barcode or string, such that the consumer'smobile device can acquire the string, via scanning it from the displayor via an application that detects it on a page within the mobiledevice.

The web site calls the web service and blocks (waits on the transactionthat is proceeding), awaiting payment confirmation: or the web siteregisters for notification once payment has been completed.

The consumer uses the retailer or mobile app to acquire the string viabarcode or other technique.

The business or mobile app connects to the web service via secureconnection, either through existing Over-The-Air (OTA) data connection,WiFi, SMS or other mechanism and presents the string.

Optionally, the consumer authenticates with the web service via theirmobile device with a secret, such as a Personal Identification Number(PIN), secure element token, biometrics or other mechanism.

The consumer is presented with a transaction summary and total amount,previously returned from the mobile transaction service.

The consumer selects a payment method and confirms payment on the mobiledevice.

Payment is confirmed, and the mobile transaction service returns apayment confirmation authorization code and any other relevantinformation required to complete the transaction to the business webapplication.

Optionally, the mobile device may receive transaction updates, anelectronic receipt or other information related to the transaction.

FIG. 2 is a diagram of a method 200 for mobile transaction processing,according to an example embodiment. The method 200 (hereinafter“transaction service”) is implemented as instructions programmed andresiding on a non-transitory computer-readable (processor-readable)storage medium and executed by one or more processors. The processorsare specifically configured and programmed to process the transactionservice. The transaction service operates over a network. The network iswired, wireless, or a combination of wired and wireless.

The transaction service executes on one or more processors of a server.In some embodiments, the transaction service in a cloud processingenvironment and is available as a cloud service over the Internet toenterprises and consumers.

In other cases, the transaction service is controlled from a server of aspecific enterprise offering mobile transaction processing.

So, the transaction service can be a third-party service offered to aplurality of enterprises or can be controlled and managed within aprocessing environment of a specific enterprise offering a specificmobile transaction processing. Both embodiments can occur simultaneouslyin the industry as well utilizing different instantiations of thetransaction service. That is, for security reasons financialinstitutions may desire to manage their own version of the transactionservice within their own controlled processing environment, where asretail establishments may opt for third-party outsourcing to utilize thetransaction service.

The processing of the transaction service interacts with consumer mobiledevice apps, applications and services of enterprise systems, and/orother third-party services utilized by consumers and/or enterprises fortransaction processing, loyalty processing, and/or other customerrelationship management processing.

At 210, the transaction service receives a request to complete atransaction. The transaction occurring between a consumer and anenterprise terminal device (e.g., website, kiosk, and the like). Receiptof the request can occur in a variety of manners.

For example, at 211, the transaction service acquires the request fromthe enterprise terminal device (or application processing thereon),where the enterprise terminal device is a website portal for anenterprise and the transaction is the completion of a shopping sessionwith a consumer on that website and the shopping cart of the consumerincludes one or more goods or services purchased from the enterprise.

In another case, at 212, the transaction service receives the request asan URL link to a specific session that is occurring between the consumerand the enterpriser terminal device.

Continuing with the embodiment of 212 and at 213, the transactionservice acquires the URL link from the mobile device of the consumer viainteractions of the consumer. In other words, the consumer sends the URLvia a mobile device to the transaction service and provides with the URLthe specific session that the consumer is engaged in with the enterpriseterminal device.

At 220, the transaction service provides a unique token back to theenterprise terminal device for uniquely identifying the transaction.This token can include a variety of information (discussed above withreference to the FIG. 1). The token permits the session for thetransaction to be identified, the transaction to be identified, theconsumer to be identified, and the enterprise or enterprise terminaldevice to be identified. In an embodiment, the token is a barcode or aQuick Response (QR) code.

In an embodiment, at 221, the transaction service generates the uniquetoken to identify the token, the consumer, the enterprise for thetransaction, and a communication session occurring between the consumerand the enterprise terminal device.

At 230, the transaction service acquires from the mobile device thetoken. The token is now signed by the mobile device.

According to an embodiment, at 231, the transaction service obtains thesigned token via a mobile app of the mobile device that scans and signsthe token from a display of a different device from that which isassociated with the mobile device.

In another case, at 232, the transaction service obtains the signedtoken via a mobile app of the mobile device that detects the transactionoccurring on a web browser of the mobile device and detects the presenceof the token once interested for completing the transaction.

At 240, the transaction service validates the signed token returned fromthe mobile device.

In an embodiment, at 241, the transaction service associates the tokenwith the consumer and a preregistered account of the consumer having thepayment details.

At 250, the transaction service causes the transaction to complete usingthe payment details associated with the consumer.

In this way, the consumer does not have to enter the payment details tocomplete a transaction.

According to an embodiment, at 251, the transaction service processesthe payment details for the transaction on behalf of the enterpriseterminal device and notifying the enterprise terminal device of thesame.

In another situation, at 252, the transaction service sends the paymentdetails to the enterprise terminal device for completing the transactionon behalf of the consumer.

FIG. 3 is a diagram of another method 300 for mobile transactionprocessing, according to an example embodiment. The method 300(hereinafter “mobile app”) is implemented as instruction and programmedwithin a non-transitory computer-readable (processor-readable) storagemedium that executes on one or more processors of a mobile device (e.g.,mobile phone, personal digital assistant (PDA), tablet, laptop, etc.);the processors of the mobile device are specifically configured toexecute the mobile app. The mobile app is operational over a network;the network is wired, wireless, or a combination of wired and wireless.

The mobile app is controlled by a consumer (customer and/or user) andinteracts with the transaction service, represented by the method 200 ofthe FIG. 2 and also interacts with an enterprise terminal device(discussed below with reference to the FIG. 4).

It is noted that the mobile app can be installed and initiated by theconsumer on the mobile device in a variety of manners before theprocessing occurs as detailed below. For instance, in one situationduring a registration process of the mobile device with a transactionservice (such as the one discussed above with reference to the FIG. 2),the mobile app is downloaded and initiated on the mobile device, hianother instance, during an initial contact by the mobile device with anenterprise terminal device of an enterprise, the customer is directed toa website of the enrollment service (discussed above with reference tothe FIG. 2) where the registration process occurs and the mobile app isdownloaded and initiated on the mobile device.

Other situations can result in the mobile app's installation as well.For instance, as part of a registration process in a loyalty programwith a specific enterprise, the consumer may agree to engage thetransaction service features. This may result in the enterprise'sregistration service in contacting the transaction service with detailsexpected by the transaction service (as discussed above) on behalf ofthe consumer, and at some later point result in the transaction servicedynamically pushing the mobile app for initiating on the mobile deviceof the consumer.

At 310, the mobile app detects a token for user in a transaction. Thetransaction occurring between a consumer of a mobile device and anenterprise, via an enterprise transaction device.

In an embodiment, at 311, the mobile app identifies the token from adisplay of another device that is different from the mobile device andthe token is scanned into the mobile device via a camera of the mobiledevice. The token displayed on a complete transaction screen for theenterprise terminal device.

In another situation, at 312, the mobile app identifies the token asbeing embedded as an image in a website page of the enterprise terminaldevice that the browser of the mobile device is accessing.

At 320, the mobile app signs the token.

At 331, the mobile app sends the signed token to a transaction server(such as the transaction service represented by the FIG. 2 above). Thetransaction service is separate and apart from the enterprise terminaldevice.

In another case, at 332, the mobile app sends the signed token to anapplication of the enterprise terminal device.

At 340, the mobile app receives an indication that the transaction waspaid for by the consumer and that the transaction completed with theenterprise terminal device.

According to an embodiment, at 350, the mobile app receives transactiondetails, loyalty information, and/or an electronic receipt for thetransaction once it completes.

FIG. 4 is a diagram of yet another method 400 for mobile transactionprocessing, according to an example embodiment. The method 300(hereinafter “enterprise terminal app”) is implemented as executableinstructions and programmed within a non-transitory computer-readable(processor-readable) storage medium that executes on one or moreprocessors of an enterprise terminal (e.g., cashier-manned device,self-service kiosk, digital sign, website of a retail, etc.); theprocessors of the enterprise terminal app are specifically configured toexecute the enterprise terminal app. The enterprise terminal app isoperational over a network; the network is wired, wireless, or acombination of wired and wireless.

The FIG. 1 described the processing for automating transactionprocessing of a consumer and/or a consumer's mobile device as a whole.The FIG. 2 described the processing from the perspective of the remoteand server/cloud based transaction service; the FIG. 3 described theprocessing from the perspective of the consumer's mobile app on aconsumer's mobile device; and the enterprise terminal app of the FIG. 4describes the processing from an enterprise's transaction systemprocessing on a retail terminal device. A consumer transaction for aretail terminal device is automated via the interaction among thetransaction service (of the FIG. 2), the mobile app (of the FIG. 3), andthe enterprise terminal app (of the FIG. 4).

At 410, the enterprise terminal app interacts with a consumer tocomplete a transaction.

According to an embodiment, at 411, the enterprise terminal appinteracts with the consumer via one or more website pages of a webportal for an enterprise. The web portal or site being viewed as anenterprise terminal device.

At 420, the enterprise terminal app, identifies a point for thetransaction where payment is required from the consumer.

At 430, the enterprise terminal app requests that a transaction serverintervene in the transaction and complete payment for the consumer. Thiscan occur out-of-band with the consumer, such as via transactionsoccurring via a mobile device of the consumer as presented above withrespect to the FIGS. 1-3.

In an embodiment, at 431, the enterprise terminal app presents a tokengenerated by the transaction service in an interface screen presented tothe consumer for completing the transaction. The mobile device processesthe token to complete the transaction.

At 440, the enterprise terminal app receives an indication that paymentfrom the consumer was received and the transaction is completed. Thepayment details processed by or acquired from the transaction server.

The above description is illustrative, and not restrictive. Many otherembodiments will be apparent to those of skill in the art upon reviewingthe above description. The scope of embodiments should therefore bedetermined with reference to the appended claims, along with the fullscope of equivalents to which such claims are entitled.

The Abstract is provided to comply with 37 C.F.R. § 1.72(b) and willallow the reader to quickly ascertain the nature and gist of thetechnical disclosure. It is submitted with the understanding that itwill not be used to interpret or limit the scope or meaning of theclaims.

In the foregoing description of the embodiments, various features aregrouped together in a single embodiment for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting that the claimed embodiments have more features than areexpressly recited in each claim. Rather, as the following claimsreflect, inventive subject matter lies in less than all features of asingle disclosed embodiment. Thus the following claims are herebyincorporated into the Description of the Embodiments, with each claimstanding on its own as a separate exemplary embodiment.

The invention claimed is:
 1. A method, comprising: registering, by aregistration service of a retailer, a consumer with a loyalty program ofthe retailer; obtaining, by the registration service, permission fromthe consumer during the registering for engaging transaction features ofa transaction sever; providing, by the registration service, details ofan account of the consumer with the retailer to the transaction serverbased on the obtaining, wherein the account is maintained as apreregistered account by the transaction server; providing, by atransaction server, a mobile application, to a mobile device of theconsumer for the consumer to interact with the transaction server and aretail terminal device of the retailer; communicating between the retailterminal device of the retailer and the mobile device of the consumerusing the mobile application of the mobile device, wherein communicatingfurther includes initiating a transaction that is initiated by theconsumer through the mobile application; identifying, by the retailterminal device, a processing point for the transaction where a paymentis required from the consumer for proceeding with the transaction;sending, by the mobile application, a request for payment processing ofthe payment along with a Uniform Resource Locator (URL) link to asession between the retail terminal device and the mobile device for thetransaction to the transaction server; acquiring, by the transactionserver, the request for payment processing of the payment and the URLlink for the session; generating, by the transaction server, a tokenidentifying the consumer, the session, and the retailer; providing, bythe transaction server, the token to the retail terminal device;displaying, by the retail terminal device, the token; scanning, by themobile application of the mobile device, the token from the retailterminal device; signing, by the mobile application of the mobiledevice, the token; providing, by the mobile application of the mobiledevice, the token that is signed to the transaction server; receiving,by the transaction server, the token that is signed from the mobileapplication of the mobile device; validating, by the transaction server,that the token is signed and received from the mobile device;associating, by the transaction server, the token with the transaction,the consumer and the preregistered account of the consumer, the payment,and the retail terminal device, wherein the preregistered accountcomprising payment details; processing, by the transaction server, thepayment details completing payment for the transaction; providing, bythe transaction server, an indication to the retail terminal deviceindicating that the payment was processed for the transaction; andreceiving, by the retail terminal device, the indication.
 2. The methodof claim 1, wherein communicating further includes communicating withthe consumer through one or more website pages of a web portal for anenterprise associated with the retail terminal device.
 3. The method ofclaim 1, wherein the retail terminal device is a kiosk.